Management of memory usage using usage analytics

ABSTRACT

An approach for managing memory usage in cloud and traditional environments using usage analytics is disclosed. The approach may be implemented in a computer infrastructure including a combination of hardware and software. The approach includes determining that space is available within one or more tables which have schema definitions with string fields having a predefined length. The approach further includes creating a virtual table and mapping the available space to the virtual table for population by one or more records.

TECHNICAL FIELD

The present invention generally relates to computing systems and, moreparticularly, to methods and systems for managing memory usage in cloudand traditional environments using usage analytics.

BACKGROUND

Database schemas are designed in such a way that fields have sufficientspace to store the data. However, for most number of instances, thespaces for storing these fields are more than actually used. This, ofcourse, leads to wasted space and resources.

For example, consider a typical database schema for storing customer'saddress information, as follows:

-   -   Table CustmerAddress {        -   Addrline1 varchar(255),        -   AddrLine2 varchar(255),        -   City varchar(100),        -   PinCode varchar(10),        -   Country varchar(50),    -   };

With the above example, a computer database application can ask for adesired number of bytes from a Virtual Memory Manager (e.g., a componentof the operating system) for storing a customer's address. However, inthis example, only a few (if any) instances of the CustomerAddress Tablewould use all allocated space, specifically for fields Addrline1 andAddrline2. In such cases, resources are wasted due to the fact that allthe allocated spaces for storing the customer's address are not used.These resources (space) can be better implemented to cater to otherneeds. Also, a considerable amount of energy (i.e., electricity) needsto be consumed to keep up those unused spaces in memory or on externalstorage devices, as described herein.

A key features of a cloud based paradigm is efficient resourceutilization (achieved through virtualization, for example). Manyalgorithms exist for effective memory allocation usage at a high level.However, there are gaps in the following dimensions:

-   -   A data block which is used statically by the process might have        the following features: Table “customer” with first name as char        30, middle name as char 10, and last name as char 50. With lack        of standards to define data lengths, the designer arbitrarily        assigns data lengths and most of the times it is always higher        to mitigate the associated risks. In reality the entire reserved        space might not be used at all, thus wasting space and        resources; and    -   Commercially Off The Shelf products (COTS) have predefined data        tables; ideally the subset domains and respective tables alone        will be used. For example, a COTS application for inventory        management will have appointment management functionality and        related database tables which might not be used at all by the        enterprise.

In all of the above cases, additional energy is used in maintaining theempty unused memory i.e., memory resources are not optimally utilized.In fact, it is known that a modern 1 terabyte drive consumes about 38microwatts per megabyte. With this metric, 1 Byte would consume 0.036nanowatt. In a large ecosystem involving multiple applications thepercentage of unused memory is more which, in turn, results in the useof considerably more energy consumption.

SUMMARY

In a first aspect of the invention, a method is implemented in acomputer infrastructure including a combination of hardware andsoftware. The method comprises determining that space is availablewithin one or more tables which have schema definitions with stringfields having a predefined length. The method further comprises creatinga virtual table and mapping the available space to the virtual table forpopulation by one or more records.

In another aspect of the invention, a system is implemented in hardwareand comprises a computer infrastructure operable to: track space withinfields of one or more defined tables; create a tracker table of allavailable spaces within the one or more defined tables; create a virtualtable; and map the available spaces to the virtual table.

In an additional aspect of the invention, a computer program productcomprises a computer usable storage medium having readable program codeembodied in the storage medium. The computer program product comprisesat least one component operable to monitor space within fields of one ormore tables having a schema definition with a first space allocation.The computer program product further comprises at least one componentoperable to determine that additional space is required within one ormore of the fields. The computer program product further comprises atleast one component operable to increment a value within the one or morefields to provide the additional space.

In a further aspect of the invention, a method comprises providing acomputer infrastructure being operable to determine that space isavailable within one or more tables which have schema definitions withstring fields having a predefined length. The computer infrastructure isfurther operable to map the available space to a virtual table forpopulation by one or more records, and relinquish any space that wasmapped to the virtual table for use within the one or more tables, asneeded.

In another aspect of the invention, a computer system storage managementcomprises a CPU, a computer readable memory and a computer readablestorage media. The system comprises first program instructions todetermine that space is available within one or more tables which haveschema definitions with string fields having a predefined length. Thesystem comprises second program instructions to create a virtual table.The system comprises third program instructions to map the availablespace to a virtual table for population by one or more records. Thesystem comprises fourth program instructions to relinquish any spacethat was mapped to the virtual table for use within the one or moretables, as needed. The first through fourth program instructions arestored on the computer readable storage media for execution by the CPUvia the computer readable memory.

BRIEF DESCRIPTION OF THE SEVERAL VIEWS OF THE DRAWINGS

The present invention is described in the detailed description whichfollows, in reference to the noted plurality of drawings by way ofnon-limiting examples of exemplary embodiments of the present invention.

FIG. 1 depicts a cloud computing node according to an embodiment of thepresent invention;

FIG. 2 depicts a cloud computing environment according to embodiments ofthe present invention;

FIG. 3 depicts abstraction model layers according to embodiments of thepresent invention;

FIG. 4 shows a block diagram of implementations in accordance withaspects of the present invention;

FIG. 5 shows a display of actual space and energy utilized against aperiod of time, in order to implement aspects of the present invention;

FIG. 6 shows a display of actual usage of memory versus reserved (and/oravailable) memory, in order to implement aspects of the presentinvention;

FIG. 7 depicts an exemplary flow diagram for using available space inone or more defined tables, in accordance with aspects of the presentinvention;

FIG. 8 shows an exemplary flow diagram of a dynamic grant process inaccordance with aspects of the present invention; and

FIG. 9 shows an exemplary flow diagram for a process to fix autilization level in accordance with aspects of the present invention.

DETAILED DESCRIPTION

The present invention generally relates to computing systems and, moreparticularly, to methods and systems for managing memory usage in cloudand traditional environments using usage analytics. In accordance withaspects of the invention, the methods and systems of the presentinvention are advantageously operable, structured and/or designed toeffectively utilize space (e.g., memory) of allocated memory and/orexternal storage devices which, in turn, will allow for efficientmanagement of power consumption. For example, by implementing thepresent invention it is now possible to use all available space within adefined schema, e.g., by creating a virtual table and mapping theavailable space to the virtual table.

In an example of use, a utility (e.g., storage management engine) isprovided as part of a database system, to more efficiently andeffectively manage used and unused space within the database.Illustratively, in embodiments, the utility manages space in thedatabase system, where a database administrator defines schemas withstring fields having a certain length, and which all of the allocatedlength (length as per the schema definition) is not used by each entryin the record. This can be implemented within a traditional or cloudbased environment, based on a user's permission.

In more specific embodiments, the management of the space can beexecuted in such a way that all spaces, as per the schema definition,are provided at the usage end. This can be accomplished by assigningavailable space within the defined tables for use in a virtual tableand, when needed again by the table, relinquishing such space within thevirtual table. For example, the utility of the present invention cantrack available (e.g., unused) space within the database, and assign ormap the available space to a virtual table. The available space can thenbe relinquished and used per the original schema definition, whenneeded, thus ensuring that all spaces, per the defined schema, can beused by the end user, e.g., the end user can use all or a portion of thecharacter strings defined in the original schema definition.Accordingly, in implementation, as and when a user does not take up allof the space as per the permitted schema definition, the utility of thepresent invention will relinquish the space to a virtual table, forexample, so that the space can be more efficiently used, and then whenneeded at a later time, relinquish this space from the virtual tableback to the original table.

In embodiments, the utility of the present invention can be a componentof database system. In this way, the database system administrator cantake advantage of the utility for their chosen schemas, therebyacknowledging the management of space for the specific schemas. For theend user of the database, the usage of this functionality would betransparent. That is, the end user would still get the spaces availableas per schema definitions; however, the utility would maintain track ofactual usage of the spaces of managed schemas, and would make use ofunused spaces to cater to other needs.

Cloud Computing

It is understood in advance that although this disclosure includes adetailed description on cloud computing, implementation of the teachingsrecited herein are not limited to a cloud computing environment. Rather,embodiments of the present invention are capable of being implemented inconjunction with any other type of computing environment now known orlater developed.

For convenience, the Detailed Description includes the followingdefinitions which have been derived from the “Draft NIST WorkingDefinition of Cloud Computing” by Peter Mell and Tim Grance, dated Oct.7, 2009, which is cited in an IDS filed herewith, and a copy of which isattached thereto.

Cloud computing is a model of service delivery for enabling convenient,on-demand network access to a shared pool of configurable computingresources (e.g. networks, network bandwidth, servers, processing,memory, storage, applications, virtual machines, and services) that canbe rapidly provisioned and released with minimal management effort orinteraction with a provider of the service. This cloud model may includeat least five characteristics, at least three service models, and atleast four deployment models.

Characteristics are as follows:

On-demand self-service: a cloud consumer can unilaterally provisioncomputing capabilities, such as server time and network storage, asneeded automatically without requiring human interaction with theservice's provider.

Broad network access: capabilities are available over a network andaccessed through standard mechanisms that promote use by heterogeneousthin or thick client platforms (e.g., mobile phones, laptops, and PDAs).

Resource pooling: the provider's computing resources are pooled to servemultiple consumers using a multi-tenant model, with different physicaland virtual resources dynamically assigned and reassigned according todemand. There is a sense of location independence in that the consumergenerally has no control or knowledge over the exact location of theprovided resources but may be able to specify location at a higher levelof abstraction (e.g., country, state, or datacenter).

Rapid elasticity: capabilities can be rapidly and elasticallyprovisioned, in some cases automatically, to quickly scale out andrapidly released to quickly scale in. To the consumer, the capabilitiesavailable for provisioning often appear to be unlimited and can bepurchased in any quantity at any time.

Measured service: cloud systems automatically control and optimizeresource use by leveraging a metering capability at some level ofabstraction appropriate to the type of service (e.g., storage,processing, bandwidth, and active user accounts). Resource usage can bemonitored, controlled, and reported providing transparency for both theprovider and consumer of the utilized service.

Service Models are as follows:

Software as a Service (SaaS): the capability provided to the consumer isto use the provider's applications running on a cloud infrastructure.The applications are accessible from various client devices through athin client interface such as a web browser (e.g., web-based e-mail).The consumer does not manage or control the underlying cloudinfrastructure including network, servers, operating systems, storage,or even individual application capabilities, with the possible exceptionof limited user-specific application configuration settings.

Platform as a Service (PaaS): the capability provided to the consumer isto deploy onto the cloud infrastructure consumer-created or acquiredapplications created using programming languages and tools supported bythe provider. The consumer does not manage or control the underlyingcloud infrastructure including networks, servers, operating systems, orstorage, but has control over the deployed applications and possiblyapplication hosting environment configurations.

Infrastructure as a Service (IaaS): the capability provided to theconsumer is to provision processing, storage, networks, and otherfundamental computing resources where the consumer is able to deploy andrun arbitrary software, which can include operating systems andapplications. The consumer does not manage or control the underlyingcloud infrastructure but has control over operating systems, storage,deployed applications, and possibly limited control of select networkingcomponents (e.g., host firewalls).

Deployment Models are as follows:

Private cloud: the cloud infrastructure is operated solely for anorganization. It may be managed by the organization or a third party andmay exist on-premises or off-premises.

Community cloud: the cloud infrastructure is shared by severalorganizations and supports a specific community that has shared concerns(e.g., mission, security requirements, policy, and complianceconsiderations). It may be managed by the organizations or a third partyand may exist on-premises or off-premises.

Public cloud: the cloud infrastructure is made available to the generalpublic or a large industry group and is owned by an organization sellingcloud services.

Hybrid cloud: the cloud infrastructure is a composition of two or moreclouds (private, community, or public) that remain unique entities butare bound together by standardized or proprietary technology thatenables data and application portability (e.g., cloud bursting forload-balancing between clouds).

A cloud computing environment is service oriented with a focus onstatelessness, low coupling, modularity, and semantic interoperability.At the heart of cloud computing is an infrastructure comprising anetwork of interconnected nodes.

Referring now to FIG. 1, a schematic of an example of a cloud computingnode is shown. Cloud computing node 10 is only one example of a suitablecloud computing node and is not intended to suggest any limitation as tothe scope of use or functionality of embodiments of the inventiondescribed herein. Regardless, cloud computing node 10 is capable ofbeing implemented and/or performing any of the functionality set forthhereinabove. FIG. 1 can also represent a computing infrastructurecapable of performing and/or implementing tasks and/or functions of themethods described herein.

In cloud computing node 10 there is a computer system/server 12, whichis operational with numerous other general purpose or special purposecomputing system environments or configurations. Examples of well-knowncomputing systems, environments, and/or configurations that may besuitable for use with computer system/server 12 include, but are notlimited to, personal computer systems, server computer systems, thinclients, thick clients, hand-held or laptop devices, multiprocessorsystems, microprocessor-based systems, set top boxes, programmableconsumer electronics, network PCs, minicomputer systems, mainframecomputer systems, and distributed cloud computing environments thatinclude any of the above systems or devices, and the like.

Computer system/server 12 may be described in the general context ofcomputer system-executable instructions, such as program modules, beingexecuted by a computer system. Generally, program modules may includeroutines, programs, objects, components, logic, data structures, and soon that perform particular tasks or implement particular abstract datatypes. Computer system/server 12 may be practiced in distributed cloudcomputing environments where tasks are performed by remote processingdevices that are linked through a communications network. In adistributed cloud computing environment, program modules may be locatedin both local and remote computer system storage media including memorystorage devices.

As shown in FIG. 1, computer system/server 12 in cloud computing node 10is shown in the form of a general-purpose computing device. Thecomponents of computer system/server 12 may include, but are not limitedto, one or more processors or processing units 16, a system memory 28,and a bus 18 that couples various system components including systemmemory 28 to processor 16. In embodiments, the computer system/server 12comprises or communicates with a storage management engine 80 (alsoreferred to as “Energy optimizer for memory” (EOFM)), as described ingreater detail herein.

Bus 18 represents one or more of any of several types of bus structures,including a memory bus or memory controller, a peripheral bus, anaccelerated graphics port, and a processor or local bus using any of avariety of bus architectures. By way of example, and not limitation,such architectures include Industry Standard Architecture (ISA) bus,Micro Channel Architecture (MCA) bus, Enhanced ISA (EISA) bus, VideoElectronics Standards Association (VESA) local bus, and PeripheralComponent Interconnects (PCI) bus.

Computer system/server 12 typically includes a variety of computersystem readable media. Such media may be any available media that isaccessible by computer system/server 12, and it includes both volatileand non-volatile media, removable and non-removable media. System memory28 can include computer system readable media in the form of volatilememory, such as random access memory (RAM) 30 and/or cache memory 32.Computer system/server 12 may further include otherremovable/non-removable, volatile/non-volatile computer system storagemedia. By way of example only, storage system 34 can be provided forreading from and writing to a non-removable, non-volatile magnetic media(not shown and typically called a “hard drive”). Although not shown, amagnetic disk drive for reading from and writing to a removable,non-volatile magnetic disk (e.g., a “floppy disk”), and an optical diskdrive for reading from or writing to a removable, non-volatile opticaldisk such as a CD-ROM, DVD-ROM or other optical media can be provided.In such instances, each can be connected to bus 18 by one or more datamedia interfaces. As will be further depicted and described below,memory 28 may include at least one program product having a set (e.g.,at least one) of program modules that are configured to carry out thefunctions of embodiments of the invention.

Program/utility 40, having a set (at least one) of program modules 42,may be stored in memory 28 by way of example, and not limitation, aswell as an operating system, one or more application programs, otherprogram modules, and program data. Each of the operating system, one ormore application programs, other program modules, and program data orsome combination thereof, may include an implementation of a networkingenvironment. Program modules 42 generally carry out the functions and/ormethodologies of embodiments of the invention as described herein. Forexample, some or all of the functions of the storage management engine80 may be implemented as one or more of the program modules 42.Additionally, the storage management engine 80 may be implemented asseparate dedicated processors or a single or several processors toprovide the functionality described herein. The storage managementengine 80 can be implemented in a graphical user interface (GUI), e.g.,display 24, which resides in any computing system such as that shown inFIG. 1, as an example. The display 24 can include a user interface suchas a keyboard, mouse and/or touch screen.

In embodiments, the storage management engine 80 manages memory usage incloud and traditional environments using usage analytics. Inembodiments, the storage management engine 80 can reside in the storagesystem 34; for example, IBM® Blue Stack® (IBM and Blue Stack aretrademarks of International Business Machines, in the U.S. and/orworldwide) or Independent Software Vendors (ISV) database servers. Inimplementation, the storage management engine 80 manages space in thestorage system, where developers and/or administrators define schemaswith string fields having a certain length, and which all of theallocated length (length as per the schema definition) is not used byeach entry in the record. Alternatively, the storage management engine80 can allocate additional space to the string fields, when necessary,as discussed in more detail herein.

In embodiments, the storage management engine 80 can manage the unusedspaces based on a user's permission. This is accomplished, at least inpart, by maintaining track of actual usage of the spaces of managedschemas. More specifically, in implementation, the storage managementengine 80 includes an internal mapper, which maintains information aboutunused spaces, in extent based format, such as (starting location,length, etc.), and maps this information to a virtual table. In thisway, the storage management engine 80 can make use of available space ina virtual table, in a dynamic manner. In further embodiments, thestorage management engine 80 can create variable length character fieldsto more efficiently use the space within the defined schema.

In more specific embodiments, the storage management engine 80 isoperable, structured and/or designed to provide the followingfunctionality:

-   -   Keep track of the actual used memory space against reserved        space and, when required, allocate unused space to and from one        or more virtual tables;    -   When triggered by the user, display actual space and energy        utilized against the period of time (see, e.g., FIG. 5);    -   Allow the user to select the percentage of savings and        internally leverage the unused space thus saving space and        costs;    -   Allow a user to define which field and/or spaces within a        particular field may or may not be given away to be utilized        elsewhere; and    -   Easily visualize actual versus reserved and/or unused memory        (see, e.g., FIG. 6).

Accordingly, by implementing the storage management engine 80 of thepresent invention, it is now possible to overcome the basic problem ofineffective memory utilization and the associated energy spent inmaintaining such unused memory and/or storage space. As to energyconsumption, a considerable amount of energy (i.e., electricity) will besaved in that the storage system (e.g., database) no longer needs to beconsumed to keep up those unused spaces in memory or on external storagedevices.

Computer system/server 12 may also communicate with one or more externaldevices 14 such as a keyboard, a pointing device, a display 24, etc.;one or more devices that enable a user to interact with computersystem/server 12; and/or any devices (e.g., network card, modem, etc.)that enable computer system/server 12 to communicate with one or moreother computing devices. Such communication can occur via I/O interfaces22. Still yet, computer system/server 12 can communicate with one ormore networks such as a local area network (LAN), a general wide areanetwork (WAN), and/or a public network (e.g., the Internet) via networkadapter 20. As depicted, network adapter 20 communicates with the othercomponents of computer system/server 12 via bus 18. It should beunderstood that although not shown, other hardware and/or softwarecomponents could be used in conjunction with computer system/server 12.Examples, include, but are not limited to: microcode, device drivers,redundant processing units, external disk drive arrays, RAID (redundantarray of inexpensive disks or redundant array of independent disks)systems, tape drives, and data archival storage systems, etc.

Aspects of the present invention are described below with reference toflowchart illustrations and/or block diagrams of methods, apparatus(systems) and computer program products according to embodiments of theinvention. It will be understood that each block of the flowchartillustrations and/or block diagrams, and combinations of blocks in theflowchart illustrations and/or block diagrams, can be implemented bycomputer program instructions. These computer program instructions maybe provided to a processor of a general purpose computer, specialpurpose computer, or other programmable data processing apparatus toproduce a machine, such that the instructions, which execute via theprocessor of the computer or other programmable data processingapparatus, create means for implementing the functions/acts specified inthe flowchart and/or block diagram block or blocks.

These computer program instructions may also be stored in a computerreadable medium that can direct a computer, other programmable dataprocessing apparatus, or other devices to function in a particularmanner, such that the instructions stored in the computer readablemedium produce an article of manufacture including instructions whichimplement the function/act specified in the flowchart and/or blockdiagram block or blocks.

The computer program instructions may also be loaded onto a computer,other programmable data processing apparatus, or other devices to causea series of operational steps to be performed on the computer, otherprogrammable apparatus or other devices to produce a computerimplemented process such that the instructions which execute on thecomputer or other programmable apparatus provide processes forimplementing the functions/acts specified in the flowchart and/or blockdiagram block or blocks.

Referring now to FIG. 2, illustrative cloud computing environment 50 isdepicted. As shown, cloud computing environment 50 comprises one or morecloud computing nodes 10 with which local computing devices used bycloud consumers, such as, for example, personal digital assistant (PDA)or cellular telephone 54A, desktop computer 54B, laptop computer 54C,and/or automobile computer system 54N may communicate. Nodes 10 maycommunicate with one another. They may be grouped (not shown) physicallyor virtually, in one or more networks, such as Private, Community,Public, or Hybrid clouds as described hereinabove, or a combinationthereof. This allows cloud computing environment 50 to offerinfrastructure, platforms and/or software as services for which a cloudconsumer does not need to maintain resources on a local computingdevice. It is understood that the types of computing devices 54A-N shownin FIG. 2 are intended to be illustrative only and that computing nodes10 and cloud computing environment 50 can communicate with any type ofcomputerized device over any type of network and/or network addressableconnection (e.g., using a web browser).

Referring now to FIG. 3, a set of functional abstraction layers providedby cloud computing environment 50 (FIG. 2) is shown. It should beunderstood in advance that the components, layers, and functions shownin FIG. 3 are intended to be illustrative only and embodiments of theinvention are not limited thereto. As depicted, the following layers andcorresponding functions are provided.

Hardware and software layer 60 includes hardware and softwarecomponents. Examples of hardware components include mainframes, in oneexample IBM® zSeries® systems; RISC (Reduced Instruction Set Computer)architecture based servers, in one example IBM pSeries® systems; IBMxSeries® systems; IBM BladeCenter® systems; storage devices; networksand networking components. Examples of software components includenetwork application server software, in one example IBM WebSphere®application server software; and database software, in one example IBMDB2® database software. (IBM, zSeries, pSeries, xSeries, BladeCenter,WebSphere, and DB2 are trademarks of International Business MachinesCorporation registered in many jurisdictions worldwide).

Virtualization layer 62 provides an abstraction layer from which thefollowing examples of virtual entities may be provided: virtual servers;virtual storage; virtual networks, including virtual private networks;virtual applications and operating systems; and virtual clients.

In one example, management layer 64 may provide the functions describedbelow. Resource provisioning provides dynamic procurement of computingresources and other resources that are utilized to perform tasks withinthe cloud computing environment. Metering and Pricing provide costtracking as resources are utilized within the cloud computingenvironment, and billing or invoicing for consumption of theseresources. In one example, these resources may comprise applicationsoftware licenses. Security provides identity verification for cloudconsumers and tasks, as well as protection for data and other resources.User portal provides access to the cloud computing environment forconsumers and system administrators. Service level management providescloud computing resource allocation and management such that requiredservice levels are met. Service Level Agreement (SLA) planning andfulfillment provide pre-arrangement for, and procurement of, cloudcomputing resources for which a future requirement is anticipated inaccordance with an SLA.

Workloads layer 66 provides examples of functionality for which thecloud computing environment may be utilized. Examples of workloads andfunctions which may be provided from this layer include: mapping andnavigation; software development and lifecycle management; virtualclassroom education delivery; data analytics processing; transactionprocessing; and management of unused space. In accordance with aspectsof the invention, the management of unused space workload/functionoperates to perform one or more of the processes described herein,including but not limited to:

-   -   Keep track of the actual used memory space against reserved        and/or unused space and, when required, allocate unused space to        and from one or more virtual tables;    -   When triggered by the user, display the actual space and energy        utilized against the period of time;    -   Allow the user to select the percentage of savings and        internally leverage the unused space thus saving space and        costs;    -   Allow a user to define which field and/or spaces within a        particular field may or may not be given away to be get utilized        elsewhere; and    -   Easily visualize actual versus reserved memory.

As will be appreciated by one skilled in the art, aspects of the presentinvention, including the storage management engine 80 and thefunctionality provided therein, may be embodied as a system, method orcomputer program product. Accordingly, aspects of the present inventionmay take the form of an entirely hardware embodiment, an entirelysoftware embodiment (including firmware, resident software, micro-code,etc.) or an embodiment combining software and hardware aspects that mayall generally be referred to herein as a “circuit,” “module” or“system.” Furthermore, aspects of the present invention may take theform of a computer program product embodied in one or more computerreadable medium(s) having computer readable program code embodiedthereon.

Any combination of one or more computer readable medium(s) may beutilized. The computer readable medium may be a computer readable signalmedium or a computer readable storage medium. A computer readablestorage medium may be, for example, but not limited to, an electronic,magnetic, optical, electromagnetic, infrared, or semiconductor system,apparatus, or device, or any suitable combination of the foregoing. Morespecific examples (a non-exhaustive list) of the computer readablestorage medium would include the following: an electrical connectionhaving one or more wires, a portable computer diskette, a hard disk, arandom access memory (RAM), a read-only memory (ROM), an erasableprogrammable read-only memory (EPROM or Flash memory), an optical fiber,a portable compact disc read-only memory (CD-ROM), an optical storagedevice, a magnetic storage device, or any suitable combination of theforegoing. In the context of this document, a computer readable storagemedium may be any tangible medium that can contain or store a programfor use by or in connection with an instruction execution system,apparatus, or device.

A computer readable signal medium may include a propagated data signalwith computer readable program code embodied therein, for example, inbaseband or as part of a carrier wave. Such a propagated signal may takeany of a variety of forms, including, but not limited to,electro-magnetic, optical, or any suitable combination thereof. Acomputer readable signal medium may be any computer readable medium thatis not a computer readable storage medium and that can communicate,propagate, or transport a program for use by or in connection with aninstruction execution system, apparatus, or device.

Program code embodied on a computer readable medium may be transmittedusing any appropriate medium, including but not limited to wireless,wireline, optical fiber cable, RF, etc., or any suitable combination ofthe foregoing.

Computer program code for carrying out operations for aspects of thepresent invention may be written in any combination of one or moreprogramming languages, including an object oriented programming languagesuch as Java, Smalltalk, C++ or the like and conventional proceduralprogramming languages, such as the “C” programming language or similarprogramming languages. The program code may execute entirely on theuser's computer, partly on the user's computer, as a stand-alonesoftware package, partly on the user's computer and partly on a remotecomputer or entirely on the remote computer or server. In the latterscenario, the remote computer may be connected to the user's computerthrough any type of network, including a local area network (LAN) or awide area network (WAN), or the connection may be made to an externalcomputer (for example, through the Internet using an Internet ServiceProvider).

FIG. 4 shows a block diagram implementing aspects of the presentinvention. Specifically, in FIG. 4, the storage management engine 80 isshown implemented in a storage system 34. The storage system 34 can be,for example, any database system. The functionality of the storagemanagement engine 80 can be interfaced with a display device 24, whichincludes any type of user interface, e.g., keyboard, mouse and/or touchscreen implementation.

In non-limiting exemplary embodiments, the storage management engine 80will monitor tables 100 a, 100 b and 100 c, which were created by adatabase manager or administrator. Although three tables are shown, itshould be understood by those of skill in the art that the database caninclude any number of tables, with any number of fields of any number ofcharacter lengths, as defined by the database administrator for aparticular database configuration. In embodiments, the table 100 adefines fields for customer information, e.g., first name, middle nameand last name, in addition to an identifier. In embodiments, each of thedefined fields can contain a certain character length, as defined by thedatabase manager. For example, in table 100 a, first name=30, middlename=30, last name=50 and identifier=40. The table 100 b defines fieldsfor customer information, which includes, e.g., driver license=50,passport=30, social security number=50 and senior citizen number=40. Thetable 100 c defines fields for customer address, which includes, e.g.,door number=50, street first=30, street middle=50, city=40, postcode=10and country=50.

As should be understood by those of skill in the art, each of the fieldsof each of the tables may be designed to provide ample space for dataentry; however, it is very common that the database administratorprovides more space than is typically required for each of these fieldsin order to mitigate risk. As such, it is common that the database willhave available (e.g., unused) space, which can now be allocated to otherneeds, by implementing the present invention as further described below.Specifically, still referring to FIG. 4, the storage management engine80 will create a tracker table 110 which will collect information fromthe tables 100 a-100 c (e.g., 100 a-100 n). More specifically, thetracker table 110 will keep track of all of the used (or unused) space,e.g., entered records, of tables 100 a-100 c, including the amount ofcharacters used for each field. For example, in the illustration shown,the tracker table 110 notes the following space (e.g., characterlengths) is available for customer information (table 100 a): firstname=15, middle name=5, last name=30 and identifier=20. Additional spaceis also shown to be available for tables 100 b and 100 c.

By a subtractive method, the storage management engine 80 will determinethat there is unused space available for reallocation from the table 100a; that is, the following is used space, based on the original characterlengths defined in table 100 a: first name=15, middle name=25, lastname=20 and identifier=20. In embodiments, the display 24 can visuallyrepresent the unused space versus reserved memory, as well as actualspace and energy utilized against the period of time. (See, e.g., FIGS.5 and 6.)

In embodiments, using the display and accompanying user interface, theuser can now select certain options in order to manage the unused spaceof the tables 100 a-100 c. For example, the user can select an option touse a certain percentage of the unused space of the tables 100 a-100 c.In the illustrative example of FIG. 4, for example, based on the userselected option, the storage management engine 80 can create a virtualtable 115, from the available space. To do this, an internal mapper 120will map the unused spaces in the tables 100 a-100 c to the virtualtable 115 (e.g., labeled Customer Contact). Thus, the virtual table 115can be defined to include fields that are virtually mapped to availablespaces within the tables 100 a-100 c. In embodiments, the internalmapper 120 can map the space required through split mechanisms, e.g.,combine two available spaces to cater to one records need. As should beunderstood by those of skill in the art, the virtual tables can becreated during off peak time per a schedule or when peak load isreduced, in order to more efficiently use power.

In further embodiments, the processes of the present invention can beautomated through a dynamic grant process. In the dynamic grant process,a minimum value and an increment value can be configured, for certainfields of any of the tables 100 a-100 c. For example, for each field ina table, the administrator can set upper and lower bounds of size forthe field, which allows the system to dynamically change the size of thefield via a dynamic create/alter process. This allows the databaseadministrator to initially create a field with a minimum length andincrement the size of the fields based on the parameters defined by thedatabase administrator (or developer). This type of process, e.g.,algorithm, can be extended to become complex for allotment of memory andthus more power savings.

By way of non-limiting illustrative example:

CREATE TABLE CustomerAddress ( DoorNumber varchar(255) lower (50)increment (25), StreetFirst varchar(255) lower(30) increment (2),StreetMiddle varchar(255) lower(50) increment(10), City varchar(255)lower(40) increment(10), PostCode( varchar10), Country varchar (50) )

In the above example, the DoorNumber would initially be created with asize of 50. When an insert request comes in for the doornumber field,the database can alter itself to increase the size of the field by 25 orit can create a temporary table called CustomerAddressTMP that allows itto have a temporary table with DoorNumber varchar(75) orDoorNumber(255). This will allow the database to either allocate a fullfield or the incremented field. The database can also merge the tablesduring off peak time per a schedule or when peak load is reduced. Inembodiments, some fields may not be variable, e.g., PostCode and Countryfields. Instead, these fields are a hard set and cannot be altered, asit may be advantageous to have a preset, immutable field length.

The dynamic grant process can also be implemented with the use of thevirtual tables. For example, after incrementing a certain field, thetracker table can be used to determine if there is any available space,and the internal mapper 120 can map the available (e.g., unused) spaceswithin the defined schema to the virtual table. In this way, any unusedspace, as increased through the incremental processes of the presentinvention, can be used by allocating such spaces to the virtual table.This will minimize any energy consumption needed to maintain unusedspace.

Accordingly, in embodiments of the present invention, resource sharingcan now be provided and/or leveraged by the cloud (through distributedand grid computing) to effectively and efficiently manage resourceutilization. For example, using the processes of the present invention,it is now possible to allocate data spaces in a dynamic manner specifiedby the above processes. This, in turn, results in the proper utilizationof memory and/or storage and the associated maintenance of power, aswell as allowing alteration of off the shelf based products which are bydefault shipped with pre-defined database tables that are notefficiently managed and used, thereby impacting effective resourceutilization and associated power.

FIG. 5 shows a display of actual space and energy utilized against aperiod of time. More specifically, FIG. 5 is representative of howutilization level value and memory can be re-used, and fluctuate over atime-line. It should be understood that the display of FIG. 5 can beused to allow the user to select the percentage of savings so that thesystems and processes of the present invention can internally leveragethe unused space thus saving space and costs. This display can also beused to determine when to merge tables during off peak time per aschedule or when peak load is reduced.

In one implementation, FIG. 5 can be representative of values againstrunning time; memory required by defined tables, and how much was theutilization level. In embodiments, the utilization level would provideadministrator information about how much percentage of unused memory isbeing utilized for other needs. As an example, 0% Utilization Level canrefer to the EOFM basically being disabled and 100% means all unusedmemory is being utilized by the present invention. In embodiments, theEOFM would collect data about various values of memory (as mentionedbelow) from the internal tracker. For example, the following informationcan be tracked:

(i) memory required by defined tables;

(ii) memory actually getting utilized by EOFM to cater to other needs;and

(iii) memory which is still available to be reused somewhere else.

In embodiments, the graphical user interface (GUI), e.g., display 24, ofthe present invention can be used by a user to can change theutilization level (e.g., from 0%-100%), where 0 indicates that unusedmemory is not to be used for virtual tables and 100 indicates that allthe unused memory can be used from the defined tables. Thus, it ispossible that an administrator can set the memory utilization level forthe EOFM, in accordance with aspects of the present invention.

FIG. 6 shows a display of actual usage of memory versus reserved memory(memory which can be allocated to the virtual table as shown, forexample, in FIG. 4). It should be understood by those of skill in theart that the display of FIG. 6 can be used to allow the user to select apercentage or specific unused allocated areas which should and shouldnot be mapped to the virtual table. This display can also be used todetermine when to merge tables during off peak time per a schedule orwhen peak load is reduced.

More specifically, in FIG. 6, the non-shaded areas represent memoryareas which may be allocated to any number of tables and/or functions.On the other hand, the lightly shaded areas represent memory areasallocated to a specific table, e.g., customer address table shown inFIG. 4, and which are in use; whereas, the darkly shaded areas representmemory areas allocated to a specific table, e.g., customer address tableshown in FIG. 4, and which are not in use. In embodiments, these unusedallocated areas can represent entire unused fields or a number ofcharacters within the field that are not in use, and which can now beallocated and mapped by the storage management engine to a virtualtable. In this way, the unused allocated areas can now be managed andefficiently used by the systems and processes of the present invention.This table can also be used to increment the values, when it isdetermined that additional space is needed within a particular field ofa particular table or tables.

Flow Diagrams

FIGS. 7-9 shows an exemplary flow for performing aspects of the presentinvention. The steps of FIGS. 7-9 may be implemented in any of theenvironments of FIGS. 1-4, for example. The flowcharts and blockdiagrams in the Figures illustrate the architecture, functionality, andoperation of possible implementations of systems, methods and computerprogram products according to various embodiments of the presentinvention. In this regard, each block in the flowchart or block diagramsmay represent a module, segment, or portion of code, which comprises oneor more executable instructions for implementing the specified logicalfunction(s). It should also be noted that, in some alternativeimplementations, the functions noted in the block may occur out of theorder noted in the figures. For example, two blocks shown in successionmay, in fact, be executed substantially concurrently, or the blocks maysometimes be executed in the reverse order, depending upon thefunctionality involved. It will also be noted that each block of theblock diagrams and/or flowchart illustration, and combinations of blocksin the block diagrams and/or flowchart illustration, can be implementedby special purpose hardware-based systems that perform the specifiedfunctions or acts, or combinations of special purpose hardware andcomputer instructions.

Furthermore, the invention can take the form of a computer programproduct accessible from a computer-usable or computer-readable mediumproviding program code for use by or in connection with a computer orany instruction execution system. The software and/or computer programproduct can be implemented in the environment of FIGS. 1-4. For thepurposes of this description, a computer-usable or computer readablemedium can be any apparatus that can contain, store, communicate,propagate, or transport the program for use by or in connection with theinstruction execution system, apparatus, or device. The medium can be anelectronic, magnetic, optical, electromagnetic, infrared, orsemiconductor system (or apparatus or device) or a propagation medium.Examples of a computer-readable storage medium include a semiconductoror solid state memory, magnetic tape, a removable computer diskette, arandom access memory (RAM), a read-only memory (ROM), a rigid magneticdisk and an optical disk. Current examples of optical disks includecompact disk-read only memory (CD-ROM), compact disc-read/write (CD-R/W)and DVD.

FIG. 7 depicts an exemplary flow for using available space in one ormore defined tables, in accordance with aspects of the presentinvention. At step 700, the processes of the present invention monitoror track the space within one or more defined fields of one or moretables having a definition schema. At step 705, the processes create atracker table of all of the available spaces within the one or moretables. At step 710, the processes of the present invention determinewhich spaces are available (e.g., unused) within the fields of each ofthe tables and maps these available spaces to a virtual table. At step715, the virtual table can be populated with records. At step 720, adetermination is made as to whether any space is needed in theoriginally defined table(s). If so, at step 725, the processes of thepresent invention will relinquish the spaces from the virtual table, foruse in the originally defined table(s). If the determination is negativeat step 720, the process can revert to step 700. At optional step 730,the processes of the present invention can merge tables during off peaktime per a schedule or when peak load is reduced. The processes can thenrevert to step 700.

FIG. 8 shows a flow diagram of a dynamic grant process in accordancewith aspects of the present invention. At step 800, the processes of thepresent invention monitor or track the space within fields of one ormore defined tables (which have a first provided value of space). Atstep 805, a determination is made as to whether additional space isrequired within the one or more tables. If not, the process will end atstep 810. Alternatively, the processes can continue to step 710 of FIG.7. If additional space is required in any of the fields of the one ormore tables, at step 815, the processes will increment the values withinthe defined fields by a predetermined character length, e.g., provide anadditional 25 characters. At step 820, the table can be populated withrecords within the available spaces. The steps of 805-820 can repeat. Atoptional step 825, the processes of the present invention can mergetables during off peak time per a schedule or when peak load is reduced.

FIG. 9 shows an exemplary flow diagram for a process to fix autilization level in accordance with aspects of the present invention.More specifically, the process shown in FIG. 9 can be provided for adatabase administrator implementing the EOFM of the present invention,to fix the utilization level. In embodiments, the processes can beprovided on a front-end of the EOFM component. At step 900, the processbegins. At step 905, a decision is made as to whether the utilization isto be changed. If no changes, the process ends at step 910. If there isto be a change, at step 915, the processes of the present invention willprovide a utilization level value. At step 920, a decision is made as towhether the utilization is within a predetermined set of values, e.g., 1and 100. If so, the utilization level value would be passed on to themanagement engine, at step 925, where it knows about how much memory isbeing utilized, and how much memory is still un-used and can beutilized. In embodiments, the utilization level value would act as aparameter, depending on which management engine would try to re-useun-used memory. If the value is not between the predetermined set ofvalues, the processes return to step 915.

In embodiments, a service provider, such as a Solution Integrator, couldoffer to perform the processes described herein. In this case, theservice provider can create, maintain, deploy, support, etc., thecomputer infrastructure that performs the process steps of the inventionfor one or more customers. These customers may be, for example, anybusiness that uses technology and provides or utilizes services. Inreturn, the service provider can receive payment from the customer(s)under a subscription and/or fee agreement and/or the service providercan receive payment from the sale of advertising content to one or morethird parties.

The descriptions of the various embodiments of the present inventionhave been presented for purposes of illustration, but are not intendedto be exhaustive or limited to the embodiments disclosed. Manymodifications and variations will be apparent to those of ordinary skillin the art without departing from the scope and spirit of the describedembodiments. The terminology used herein was chosen to best explain theprinciples of the embodiments, the practical application or technicalimprovement over technologies found in the marketplace, or to enableothers of ordinary skill in the art to understand the embodimentsdisclosed herein.

What is claimed:
 1. A method implemented in a computer infrastructurecomprising hardware, the method comprising: monitoring available spacewithin string fields having a predefined length within one or moretables having schema definitions; creating a virtual table with a sizebased on the available space; changing a utilization level of unusedmemory of the one or more tables; and mapping the unused memory of theone or more tables to the virtual table based on the changed utilizationlevel of the unused memory of the one or more tables.
 2. The method ofclaim 1, further comprising creating a tracker table of all availablespace within the string fields having the predefined length of the oneor more tables, and the tracker table is created by a subtractive methodwhich determines that there is unused space available for reallocationfrom the one or more tables.
 3. The method of claim 1, furthercomprising: mapping the available space in the string fields to thevirtual table for populating the virtual table within one or morerecords having a space which corresponds with the available space in thestring fields, wherein all spaces per the schema definitions areprovided at a usage end by relinquishing any space that was mapped tothe virtual table.
 4. The method of claim 1, further comprisingincrementing values of the one or more tables, when additional space isrequired for one or more fields of the one or more tables.
 5. The methodof claim 1, further comprising merging the one or more tables during offpeak time per a schedule or when peak load is reduced.
 6. The method ofclaim 1, further comprising creating variable length character fieldsfor additional space required within the one or more tables.
 7. Themethod of claim 1, further comprising displaying actual space and energyutilized against the period of time.
 8. The method of claim 1, furthercomprising performing the steps of claim 1 in a cloud environment. 9.The method of claim 1, further comprising providing a percentage of theavailable space that is mapped to the virtual table, wherein thepercentage of the available space is selected by a user.
 10. The methodof claim 1, further comprising a dynamic grant process which isconfigured to initially create a field with a minimum size within theone or more tables and then incrementing a size of the field until thesize of the field reaches a maximum size.
 11. The method of claim 1,wherein the utilization level is set by an administrator through agraphical user interface (GUI).
 12. The method of claim 1, furthercomprising populating the virtual table with at least one record. 13.The method of claim 1, wherein the mapping the unused memory of the oneor more tables to the virtual table is provided by a storage managementengine which comprises an internal mapper which maintains information ofunused spaces in an extent based format which comprises startinglocation and length.
 14. The method of claim 13, wherein the storagemanagement engine automatically and dynamically maps the unused memoryof the one or more tables to the virtual table using the storagemanagement engine in response to the utilization level of the unusedmemory being changed.
 15. The method of claim 14, wherein the storagemanagement engine creates variable length character fields for the oneor more tables having the schema definitions.
 16. The method of claim15, further comprising: receiving a selection of space within the one ormore tables through the GUI using a storage management engine; andpreventing the selection of space within the one or more tables frombeing used in the virtual table.
 17. The method of claim 16, furthercomprising displaying an off peak time per a schedule through agraphical user interface (GUI).
 18. The method of claim 17, furthercomprising displaying the unused memory and reserved memory of the oneor more tables through a graphical user interface (GUI).
 19. A systemimplemented in hardware and comprising a computer infrastructureoperable to: create a tracker table of all available space within stringfields having a predefined length of one or more tables; create avirtual table; and provide a percentage of the available space that ismapped to the virtual table, wherein the virtual table is created with asize that is based on the percentage of the available space that ismapped to the virtual table.
 20. A computer program product comprising anon-transitory computer usable storage medium having readable programembodied in the storage medium, wherein the computer program productincludes at least one component operable to: track available spacewithin string fields of one or more tables; determine whether additionalspace is required within the one or more tables; increment values withinthe string fields by a predetermined character length in response to adetermination that the additional space is required within the one ormore tables; merge the one or more tables during off peak time per aschedule; and populate the one or more tables with records within theavailable space.